View SRIX4K-W41GE_1229602.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

1/43 december 2004 srix4k 13.56mhz short range contactless memory chip with 4096 bit eeprom, anti-co llision and anti-clone functions features summary iso 14443 - 2 type b air interface compliant iso 14443 - 3 type b frame format compliant 13.56mhz carrier frequency 847khz sub-carrier frequency 106 kbit/second data transfer france telecom proprietary anti-clone function 8 bit chip_id based anticollision system 2 count-down binary counters with automated anti-tearing protection 64-bit unique identifier 4096-bit eeprom with write protect feature read block and write block (32 bits) internal tuning capacitor 1million erase/write cycles 40-year data retention self-timed programming cycle 5ms typical programming time figure 1. delivery forms wafer antenna (a3) antenna (a4) antenna (a5)
srix4k 2/43 table of contents features summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 figure 1. delivery forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 summary description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 figure 2. logic diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 table 1. signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 figure 3. die floor plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 ac1, ac0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 input data transfer from the reader to the srix4k (request frame) . . . . . . . . . . . . . . . . . . . . 7 figure 4. 10% ask modulation of the received wave. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 character transmission format for request frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 figure 5. srix4k request frame character format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 table 2. bit description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 request start of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 6. request start of frame. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 request end of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 7. request end of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 output data transfer from the srix4k to the reader (answer frame) . . . . . . . . . . . . . . . . . . . 8 figure 8. wave transmitted using bpsk sub-carrier modulation . . . . . . . . . . . . . . . . . . . . . . . . . . 8 character transmission format for answer frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 answer start of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 9. answer start of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 answer end of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 10.answer end of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 transmission frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 11.example of a complete transmission frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 crc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 figure 12.crc transmission rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 memory mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 13.srix4k memory mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 resettable otp area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 figure 14.resettable otp area (addresses 0 to 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 figure 15.write_block update in standard mode (binary format). . . . . . . . . . . . . . . . . . . . . . 12 figure 16.write_block update in reload mode (binary format) . . . . . . . . . . . . . . . . . . . . . . . 12 32-bit binary counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 17.binary counter (addresses 5 to 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 18.count down example (binary format) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 eeprom area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3/43 srix4k figure 19.eeprom (addresses 7 to 127) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 system area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 figure 20.system area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 otp_lock_reg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 fixed chip_id (option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 srix4k operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 srix4k states. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 power-off state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 ready state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 inventory state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 selected state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 deselected state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 deactivated state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 figure 21.state transition diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 anti-collision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 figure 22.srix4k chip_id description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 figure 23.description of a possible anti-collision sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 description of an anti-collision sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 3. standard anti-collision sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 figure 24.example of an anti-collision sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 anti-clone function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 srix4k commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 table 4. command code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 initiate() command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 figure 25.initiate request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 figure 26.initiate response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3 figure 27.initiate frame exchange between reader and srix4k. . . . . . . . . . . . . . . . . . . . . . . 23 pcall16() command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 figure 28.pcall16 request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4 figure 29.pcall16 response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 figure 30.pcall16 frame exchange between reader and srix4k . . . . . . . . . . . . . . . . . . . . . . 24 slot_marker(sn) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 figure 31.slot_marker request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 figure 32.slot_marker response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 figure 33.slot_marker frame exchange between reader and srix4k. . . . . . . . . . . . . . . . . 25 select(chip_id) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 figure 34.select request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 figure 35.select response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 figure 36.select frame exchange between reader and srix4k . . . . . . . . . . . . . . . . . . . . . . . 26 completion() command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 figure 37.completion request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
srix4k 4/43 figure 38.completion response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 figure 39.completion frame exchange between reader and srix4k . . . . . . . . . . . . . . . . . . 27 reset_to_inventory() command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 40.reset_to_inventory request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 41.reset_to_inventory response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 42.reset_to_inventory frame exchange between reader and srix4k . . . . . . . . . 28 read_block(addr) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 figure 43.read_block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 figure 44.read_block response format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 figure 45.read_block frame exchange between reader and srix4k . . . . . . . . . . . . . . . . . . 29 write_block (addr, data) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 figure 46.write_block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 figure 47.write_block response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 figure 48.write_block frame exchange between reader and srix4k . . . . . . . . . . . . . . . . . 30 get_uid() command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 figure 49.get_uid request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 figure 50.get_uid response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 figure 51.get_uid frame exchange between reader and srix4k . . . . . . . . . . . . . . . . . . . . . . 31 power-on state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 maximum rating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 5. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 dc and ac parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 table 6. operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 table 7. dc characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 table 8. ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 figure 52.srix4k synchronous timing, transmit and receive . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 package mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 figure 53.a3 antenna specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 table 9. a3 antenna specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 figure 54.a4 antenna specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 10. a4 antenna specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 figure 55.a5 antenna specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 11. a5 antenna specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 12. ordering information scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 8 appendix a.iso14443 type b crc calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 appendix b.srix4k command summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 figure 56.initiate frame exchange between reader and srix4k. . . . . . . . . . . . . . . . . . . . . . . 40 figure 57.pcall16 frame exchange between reader and srix4k . . . . . . . . . . . . . . . . . . . . . . 40 figure 58.slot_marker frame exchange between reader and srix4k. . . . . . . . . . . . . . . . . 40
5/43 srix4k figure 59.select frame exchange between reader and srix4k . . . . . . . . . . . . . . . . . . . . . . . 40 figure 60.completion frame exchange between reader and srix4k . . . . . . . . . . . . . . . . . . 40 figure 61.reset_to_inventory frame exchange between reader and srix4k . . . . . . . . . 41 figure 62.read_block frame exchange between reader and srix4k . . . . . . . . . . . . . . . . . . 41 figure 63.write_block frame exchange between reader and srix4k . . . . . . . . . . . . . . . . . 41 figure 64.get_uid frame exchange between reader and srix4k . . . . . . . . . . . . . . . . . . . . . . 41 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 table 13. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
srix4k 6/43 summary description the srix4k is a contactless memory, powered by an externally transmitted radio wave. it contains a 4096-bit user eeprom fabricated with stmicro- electronics cmos technology. the memory is or- ganized as 128 blocks of 32 bits. the srix4k is accessed via the 13.56mhz carrier. incoming data are demodulated and decoded from the received amplitude shift keying (ask) modulation signal and outgoing data are generated by load variation using bit phase shift keying (bpsk) coding of a 847khz sub-carrier. the received ask wave is 10% modulated. the data transfer rate between the srix4k and the reader is 106kbit/s in both re- ception and emission modes. the srix4k follows the iso 14443 part 2 type b recommendation for the radio-frequency power and signal interface. figure 2. logic diagram the srix4k is specifically designed for short range applications that need secure and re-usable products. the srix4k includes an anti-collision mechanism that allows it to detect and select tags present at the same time within range of the read- er. the anti-collision is based on a probabilistic scanning method using slot markers. the srix4k provides an anti-clone function which allows its au- thentication. using the stmicroelectronics single chip coupler, crx14, it is easy to design a reader with the authentication capability and to build a system with a high level of security. table 1. signal names the srix4k contactless eeprom can be ran- domly read and written in block mode (each block containing 32 bits). the instruction set includes the following ten commands: read_block write_block initiate pcall16 slot_marker select completion reset_to_inventory authenticate get_uid the srix4k memory is organized in three areas, as described in figure 13. . the first area is a reset- table otp (one time programmable) area in which bits can only be switched from 1 to 0. using a spe- cial command, it is possible to erase all bits of this area to 1. the second area provides two 32-bit bi- nary counters which can only be decremented from ffffffffh to 00000000h, and gives a ca- pacity of 4,294,967,296 units per counter. the last area is the eeprom memory. it is accessible by block of 32 bits and includes an auto-erase cycle during each write_block command. figure 3. die floor plan signal description ac1, ac0. the pads for the antenna coil. ac1 and ac0 must be directly bonded to the antenna. ac1 antenna coil ac0 antenna coil ai06829 ac1 srix4k ac0 power supply regulator bpsk load modulator ask demodulator 4 kbit user eeprom ai09055 ac1 ac0
7/43 srix4k data transfer input data transfer from the reader to the srix4k (request frame) the reader must generate a 13.56mhz sinusoidal carrier frequency at its antenna, with enough ener- gy to ?remote-power? the memory. the energy re- ceived at the srix4k?s antenna is transformed into a supply voltage by a regulator, and into data bits by the ask demodulator. for the srix4k to decode correctly the information it receives, the reader must 10% amplitude-modulate the 13.56mhz wave before sending it to the srix4k. this is represented in figure 4. . the data transfer rate is 106 kbits/s. figure 4. 10% ask modulation of the received wave character transmission format for request frame. the srix4k transmits and receives data bytes as 10-bit characters, with the least signifi- cant bit (b 0 ) transmitted first, as shown in figure 5. . each bit duration, an etu (elementary time unit), is equal to 9.44s (1/106khz). these characters, framed by a start of frame (sof) and an end of frame (eof), are put to- gether to form a command frame as shown in figure 11. . a frame includes an sof, commands, addresses, data, a crc and an eof as defined in the iso14443-3 type b standard. if an error is de- tected during data transfer, the srix4k does not execute the command, but it does not generate an error frame. figure 5. srix4k request frame character format table 2. bit description data bit to transmit to the 10% ask modulation of the 13.56mhz wave, generated by the reader transfer time for one data bit is 1/106 khz srix4k ai05729 bit description value b 0 start bit used to synchronize the transmission b 0 = 0 b 1 to b 8 information byte (command, address or data) the information byte is sent with the least significant bit first b 9 stop bit used to indicate the end of a character b 9 = 1 ai07664 1 etu start "0" stop "1" msb lsb information byte b0 b1 b2 b3 b4 b5 b6 b7 b8 b9
srix4k 8/43 request start of frame. the sof described in figure 6. is composed of: ? one falling edge, ? followed by 10 etus at logic-0, ? followed by a single rising edge, ? followed by at least 2 etus (and at most 3) at logic-1. figure 6. request start of frame request end of frame. the eof shown in fig- ure 7. is composed of: ? one falling edge, ? followed by 10 etus at logic-0, ? followed by a single rising edge. figure 7. request end of frame output data transfer from the srix4k to the reader (answer frame) the data bits issued by the srix4k use retro- modulation. retro-modulation is obtained by mod- ifying the srix4k current consumption at the an- tenna (load modulation). the load modulation causes a variation at the reader antenna by induc- tive coupling. with appropriate detector circuitry, the reader is able to pick up information from the srix4k. to improve load-modulation detection, data is transmitted using a bpsk encoded, 847khz sub-carrier frequency ? s as shown in fig- ure 8. , and as specified in the iso14443-2 type b standard. figure 8. wave transmitted using bpsk sub-carrier modulation ai07665 etu b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 000000000011 ai07666 etu b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 0000000000 or ai05730 data bit to be transmitted to the reader 847khz bpsk modulation generated by the srix4k bpsk modulation at 847khz during a one-bit data transfer time (1/106khz)
9/43 srix4k character transmission format for answer frame. the character format is the same as for input data transfer ( figure 5. ). the transmitted frames are made up of an sof, data, a crc and an eof ( figure 11. ). as with an input data trans- fer, if an error occurs, the reader does not issue an error code to the srix4k, but it should be able to detect it and manage the situation. the data trans- fer rate is 106 kbits/second. answer start of frame. the sof described in figure 9. is composed of: ? followed by 10 etus at logic-0 ? followed by 2 etus at logic-1 figure 9. answer start of frame answer end of frame. the eof shown in fig- ure 10. is composed of: ? followed by 10 etus at logic-0, ? followed by 2 etus at logic-1. figure 10. answer end of frame transmission frame between the request data transfer and the an- swer data transfer, all ask and bpsk modulations are suspended for a minimum time of t 0 = 128/? s . this delay allows the reader to switch from trans- mission to reception mode. it is repeated after each frame. after t 0 , the 13.56mhz carrier fre- quency is modulated by the srix4k at 847khz for a period of t 1 = 128/? s to allow the reader to syn- chronize. after t 1 , the first phase transition gener- ated by the srix4k forms the start bit (?0?) of the answer sof. after the falling edge of the answer eof, the reader waits a minimum time, t 2 , before sending a new request frame to the srix4k. figure 11. example of a complete transmission frame ai07665 etu b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 000000000011 ai07665 etu b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 000000000011 12 bits 10 bits sync 128/fs 128/fs f s =847.5khz t dr t 0 t 1 sof cmd data crc crc eof 10 bits 10 bits 10 bits 10 bits 12 bits 10 bits 10 bits 10 bits data crc crc sof eof 12 bits sof t 2 ai05731 input data transfer using ask output data transfer using bpsk sent by the reader sent by the srix4k at 106kb/s
srix4k 10/43 crc the 16-bit crc used by the srix4k is generated in compliance with the iso14443 type b recom- mendation. for further information, please see appendix a. . the initial register contents are all 1s: ffffh. the two-byte crc is present in every request and in every answer frame, before the eof. the crc is calculated on all the bytes between sof (not included) and the crc field. upon reception of a request from a reader, the srix4k verifies that the crc value is valid. if it is invalid, the srix4k discards the frame and does not answer the reader. upon reception of an answer from the srix4k, the reader should verify the validity of the crc. in case of error, the actions to be taken are the read- er designer?s responsibility. the crc is transmitted with the least significant byte first and each byte is transmitted with the least significant bit first. figure 12. crc transmission rules crc 16 (8 bits) crc 16 (8 bits) lsbit msbit lsbit msbit lsbyte msbyte ai07667
11/43 srix4k memory mapping the srix4k is organized as 128 blocks of 32 bits as shown in figure 13. . all blocks are accessible by the read_block command. depending on the write access, they can be updated by the write_block command. a write_block up- dates all the 32 bits of the block. figure 13. srix4k memory mapping block addr msb 32 bits block lsb b 31 b 24 b 23 b 16 b 15 b 8 b 7 b 0 description 0 32 bits boolean area resettable otp bits 1 32 bits boolean area 2 32 bits boolean area 3 32 bits boolean area 4 32 bits boolean area 5 32 bits binary counter count down counter 6 32 bits binary counter 7user area lockable eeprom 8user area 9user area 10 user area 11 user area 12 user area 13 user area 14 user area 15 user area 16 user area eeprom ... user area 127 user area 255 otp_lock_reg st reserved fixed chip_id (option) system otp bits uid0 64 bits uid area rom uid1
srix4k 12/43 resettable otp area in this area contains five individual 32-bit boolean words (see figure 14. for a map of the area). a write_block command will not erase the pre- vious contents of the block as the write cycle is not preceded by an auto erase cycle. this feature can be used to reset selected bits from 1 to 0. all bits previously at 0 remain unchanged. when the 32 bits of a block are all at 0, the block is empty, and cannot be updated any more. see figure 15. and figure 16. for examples of the result of the write_block command in the resettable otp area. figure 14. resettable otp area (addresses 0 to 4) figure 15. write_block update in standard mode (binary format) the five 32-bit blocks making up the resettable otp area can be erased in one go by adding an auto erase cycle to the write_block com- mand. an auto erase cycle is added each time the srix4k detects a reload command. the reload command is implemented through a specific up- date of the 32 -bit binary counter located at block address 6 (see ? 32-bit binary counters ? for de- tails). figure 16. write_block update in reload mode (binary format) block address msb b31 32-bit block b16 b15 b24 b23 b8 b7 lsb b0 description resettable otp bit 0 1 2 3 4 32-bit boolean area 32-bit boolean area 32-bit boolean area 32-bit boolean area 32-bit boolean area ai07657 ai07658 1 ... 1 1 01011 11 1 0 11 1 ... 1 0 01011 00 1 1 11 1 ... 1 0 01011 00 1 0 11 previous data stored in block data to be written new data stored in block b31 b0 ai07659 1...11 0 1011 11 1 0 11 1...11 1 1011 00 1 1 11 1...11 1 1011 00 1 1 11 previous data stored in block data to be written new data stored in block b31 b0
13/43 srix4k 32-bit binary counters the two 32-bit binary counters located at block ad- dresses 5 and 6, respectively, are used to count down from 2 32 (4096 million) to 0. the srix4k uses dedicated logic that only allows the update of a counter if the new value is lower than the previ- ous one. this feature allows the application to count down by steps of 1 or more. the initial value in the counter is ffffffffh. when the value dis- played is 00000000h, the counter is empty and cannot be reloaded. the counter is updated by is- suing the write_block command to block ad- dress 5 or 6, depending on which counter is to be updated. the write_block command writes the new 32-bit value to the counter block address. figure 18. shows examples of how the counters operate. the counter programming cycles are protected by automated anti-tearing logic. this function allows the counter value to be protected in case of power down within the programming cycle. in case of power down, the counter value is not updated and the previous value continues to be stored. figure 17. binary counter (addresses 5 to 6) figure 18. count down example (binary format) the counter with block address 6 controls the re- load command used to reset the resettable otp area (addresses 0 to 4). bits b 31 to b 21 act as an 11-bit reload counter; whenever one of these 11 bits is updated, the srix4k detects the change and adds an erase cycle to the write_block command for locations 0 to 4 (see the ? resettable otp area ? paragraph). the erase cycle remains active until a power-off or a select com- mand is issued. the srix4k?s resettable otp area can be reloaded up to 2,047 times (2 11 -1). block address msb b31 32-bit block b16 b15 b24 b23 b8 b7 lsb b0 description count down counter 5 6 32-bit binary counter 32-bit binary counter ai07660 ai07661 1...1111111111111 1...111111111111 0 1...11111111111 01 initial data 1-unit decrement 1-unit decrement b31 b0 1...11111111111 00 1...111111111 0100 1...111111111 1000 1-unit decrement 8-unit decrement increment not allowed
srix4k 14/43 eeprom area the 121 blocks between addresses 7 and 127 are eeprom blocks of 32 bits each (484 bytes in to- tal). (see figure 19. for a map of the area.) these blocks can be accessed using the read_block and write_block commands. the write_block command for the eeprom area always includes an auto-erase cycle prior to the write cycle. blocks 7 to 15 can be write-protected. write ac- cess is controlled by the 8 bits of the otp_lock_reg located at block address 255 (see ? otp_lock_reg ? for details). once protected, these blocks (7 to 15) cannot be unprotected. figure 19. eeprom (addresses 7 to 127) block address msb b31 32-bit block b16 b15 b24 b23 b8 b7 lsb b0 description lockable eeprom 7 8 9 10 11 user area user area user area user area user area ai07661b 13 14 15 16 ... user area user area user area user area user area 12 127 user area user area eeprom
15/43 srix4k system area this area is used to modify the settings of the srix4k. it contains 3 registers: otp_lock_reg, fixed chip_id and st reserved. see figure 20. for a map of this area. a write_block command in this area will not erase the previous contents. selected bits can thus be set from 1 to 0. all bits previously at 0 re- main unchanged. once all the 32 bits of a block are at 0, the block is empty and cannot be updated any more. figure 20. system area otp_lock_reg. the 8 bits, b 31 to b 24 , of the system area (block address 255) are used as otp_lock_reg bits in the srix4k. they control the write access to the 9 eeprom blocks with ad- dresses 7 to 15 as follows: ? when b 24 is at 0, blocks 7 and 8 are write- protected ? when b 25 is at 0, block 9 is write-protected ? when b 26 is at 0, block 10 is write-protected ? when b 27 is at 0, block 11 is write-protected ? when b 28 is at 0, block 12 is write-protected ? when b 29 is at 0, block 13 is write-protected ? when b 30 is at 0, block 14 is write-protected ? when b 31 is at 0, block 15 is write-protected. the otp_lock_reg bits cannot be erased. once write-protected, eeprom blocks behave like rom blocks and cannot be unprotected. fixed chip_id (option). the srix4k is provid- ed with an anti-collision feature based on a ran- dom 8-bit chip_id. prior to selecting an srix4k, an anti-collision sequence has to be run to search for the chip_id of the srix4k. this is a very flex- ible feature, however the searching loop requires time to run. for some applications, much time could be saved by knowing the value of the srix4k chip_id be- forehand, so that the srix4k can be identified and selected directly without having to run an anti-col- lision sequence. this is why the srix4k was de- signed with an optional mask setting used to program a fixed 8-bit chip_id to bits b 7 to b 0 of the system area. when the fixed chip_id option is used, the random chip_id function is disabled. block address 255 msb b31 b24 b23 32-bit block b16 b15 b8 b7 b0 lsb description otp otp_lock_reg st reserved fixed chip_id (option) ai07663
srix4k 16/43 srix4k operation all commands, data and crc are transmitted to the srix4k as 10-bit characters using ask mod- ulation. the start bit of the 10 bits, b 0 , is sent first. the command frame received by the srix4k at the antenna is demodulated by the 10% ask de- modulator, and decoded by the internal logic. prior to any operation, the srix4k must have been se- lected by a select command. each frame trans- mitted to the srix4k must start with a start of frame, followed by one or more data characters, two crc bytes and the final end of frame. when an invalid frame is decoded by the srix4k (wrong command or crc error), the memory does not re- turn any error code. when a valid frame is received, the srix4k may have to return data to the reader. in this case, data is returned using bpsk encoding, in the form of 10-bit characters framed by an sof and an eof. the transfer is ended by the srix4k sending the 2 crc bytes and the eof. srix4k states the srix4k can be switched into different states. depending on the current state of the srix4k, its logic will only answer to specific commands. these states are mainly used during the anti-colli- sion sequence, to identify and to access the srix4k in a very short time. the srix4k provides 6 different states, as described in the following paragraphs and in figure 21. . power-off state the srix4k is in power-off state when the electromagnetic field around the tag is not strong enough. in this state, the srix4k does not re- spond to any command. ready state when the electromagnetic field is strong enough, the srix4k enters the ready state. after power- up, the chip_id is initialized with a random value. the whole logic is reset and remains in this state until an initiate() command is issued. any other command will be ignored by the srix4k. inventory state the srix4k switches from the ready to the in- ventory state after an initiate() command has been issued. in inventory state, the srix4k will respond to any anti-collision com- mands: initiate(), pcall16() and slot_marker(), and then remain in the inven- tory state. it will switch to the selected state after a select(chip_id) command is issued, if the chip_id in the command matches its own. if not, it will remain in inventory state. selected state in selected state, the srix4k is active and re- sponds to all read_block(), write_block(), authenticate() and get_uid() commands. when an srix4k has entered the selected state, it no longer responds to anti-collision com- mands. so that the reader can access another tag, the srix4k can be switched to the deselected state by sending a select(chip_id2) with a chip_id that does not match its own, or it can be placed in deactivated state by issuing a com- pletion() command. only one srix4k can be in selected state at a time. deselected state once the srix4k is in deselected state, only a select(chip_id) command with a chip_id matching its own can switch it back to selected state. all other commands are ignored. deactivated state when in this state, the srix4k can only be turned off. all commands are ignored.
17/43 srix4k figure 21. state transition diagram power-off ready on field out of field chip_id 8bits = rnd inventory initiate() initiate() or pcall16() or slot_marker(sn) or select(wrong chip_id) out of field select(chip_id) selected out of field deselected deactivated select( chip_id) select(chip_id) completion() out of field out of field read_block() write_block() authenticate() get_uid() reset_to_inventory() select(chip_id) ai05733
srix4k 18/43 anti-collision the srix4k provides an anti-collision mechanism that searches for the chip_id of each device that is present in the reader field range. when known, the chip_id is used to select an srix4k individu- ally, and access its memory. the anti-collision se- quence is managed by the reader through a set of commands described in the ? srix4k opera- tion ? section: initiate() pcall16() slot_marker(). the reader is the master of the communication with one or more srix4k device(s). it initiates the tag communication activity by issuing an ini- tiate(), pcall16() or slot_marker() com- mand to prompt the srix4k to answer. during the anti-collision sequence, it might happen that two or more srix4k devices respond simultaneously, so causing a collision. the command set allows the reader to handle the sequence, to separate srix4k transmissions into different time slots. once the anti-collision sequence has completed, srix4k communication is fully under the control of the reader, allowing only one srix4k to trans- mit at a time. the anti-collision scheme is based on the defini- tion of time slots during which the srix4k devices are invited to answer with minimum identification data: the chip_id. the number of slots is fixed at 16 for the pcall16() command. for the ini- tiate() command, there is no slot and the srix4k answers after the command is issued. srix4k devices are allowed to answer only once during the anticollision sequence. consequently, even if there are several srix4k devices present in the reader field, there will probably be a slot in which only one srix4k answers, allowing the reader to capture its chip_id. using the chip_id, the reader can then establish a communication channel with the identified srix4k. the purpose of the anti-collision sequence is to allow the reader to select one srix4k at a time. the srix4k is given an 8-bit chip_id value used by the reader to select only one among up to 256 tags present within its field range. the chip_id is initialized with a random value during the ready state, or after an initiate() command in the in- ventory state. the four least significant bits ( b 0 to b 3 ) of the chip_id are also known as the chip_slot_number. this 4-bit value is used by the pcall16() and slot_marker() com- mands during the anti-collision sequence in the in- ventory state. figure 22. srix4k chip_id description each time the srix4k receives a pcall16() command, the chip_slot_number is given a new 4-bit random value. if the new value is 0000 b , the srix4k returns its whole 8-bit chip_id in its answer to the pcall16() command. the pcall16() command is also used to define the slot number 0 of the anti-collision sequence. when the srix4k receives the slot_marker(sn) command, it compares its chip_slot_number with the slot_number parameter (sn). if they match, the srix4k returns its chip_id as a re- sponse to the command. if they do not, the srix4k does not answer. the slot_marker(sn) command is used to define all the anti-collision slot numbers from 1 to 15. ai07668 b7 b6 b5 b4 b3 b2 b1 b0 8-bit chip_id b0 to b3: chip_slot_number
19/43 srix4k figure 23. description of a possible anti-collision sequence note: the value x in the answer chip_id means a random hexadecimal character from 0 to f. slot 0 slot 1 slot 2 slot n slot 15 <><> < > reader srix devices s o f e o f <-> <-> <-> <-> < > <-> <-> <-> timing t 0 + t 1 t 2 t 0 + t 1 t 2 t 3 t 0 + t 1 comment no collision time > ai09035b <> collision no answer t 2 no collision t 2 ... answer chip_id x1h e o f e o f e o f answer chip_id x0h answer chip_id xfh s o f s o f s o f s o f s o f s o f e o f e o f e o f e o f s o f s o f e o f pcall 16 request slot marker (1) slot marker (2) answer chip_id x1h slot marker (15) ...
srix4k 20/43 description of an anti-collision sequence the anti-collision sequence is initiated by the ini- tiate() command which triggers all the srix4k devices that are present in the reader field range, and that are in inventory state. only srix4k devices in inventory state will respond to the pcall16() and slot_marker(sn) anti-colli- sion commands. a new srix4k introduced in the field range during the anti-collision sequence will not be taken into account as it will not respond to the pcall16() or slot_marker(sn) command (ready state). to be considered during the anti-collision se- quence, it must have received the initiate() command and entered the inventory state. table 3. shows the elements of a standard anti- collision sequence. (see figure 24. for an exam- ple.) table 3. standard anti-collision sequence after each slot_marker() command, there may be several, one or no answers from the srix4k devices. the reader must handle all the cases and store all the chip_ids, correctly decod- ed. at the end of the anti-collision sequence, after slot_marker(15), the reader can start working with one srix4k by issuing a select() com- mand containing the desired chip_id. if a collision is detected during the anti-collision sequence, the reader has to generate a new sequence in order to identify all unidentified srix4k devices in the field. the anti-collision sequence can stop when all srix4k devices have been identified. step 1 init: send initiate(). ? if no answer is detected, go to step1. ? if only 1 answer is detected, select and access the srix4k. after accessing the srix4k, deselect the tag and go to step1. ? if a collision (many answers) is detected, go to step2. step 2 slot 0 send pcall16(). ? if no answer or collision is detected, go to step3. ? if 1 answer is detected, store the chip_id, send select() and go to step3. step 3 slot 1 send slot_marker(1). ? if no answer or collision is detected, go to step4. ? if 1 answer is detected, store the chip_id, send select() and go to step4. step 4 slot 2 send slot_marker(2). ? if no answer or collision is detected, go to step5. ? if 1 answer is detected, store the chip_id, send select() and go to step5. step n slop n send slot_marker(3 up to 14) ... ? if no answer or collision is detected, go to stepn+1. ? if 1 answer is detected, store the chip_id, send select() and go to stepn+1. step 17 slot 15 send slot_marker(15). ? if no answer or collision is detected, go to step18. ? if 1 answer is detected, store the chip_id, send select() and go to step18. step 18 all the slots have been generated and the chip_id values should be stored into the reader memory. issue the select(chip_id) command and access each identified srix4k one by one. after accessing each srix4k, switch them into deselected or deactivated state, depending on the application needs. ? if collisions were detected between step2 and step17, go to step2. ? if no collision was detected between step2 and step17, go to step1.
21/43 srix4k figure 24. example of an anti-collision sequence command tag 1 chip_id tag 2 chip_id tag 3 chip_id tag 4 chip_id tag 5 chip_id tag 6 chip_id tag 7 chip_id tag 8 chip_id comments ready state 28h 75h 40h 01h 02h feh a9h 7ch each tag gets a random chip_id initiate () 40h 13h 3fh 4ah 50h 48h 52h 7ch each tag get a new random chip_id. all tags answer: collisions 45h 12h 30h 43h 55h 43h 53h 73h all chip_slot_numbers get a new random value pcall16() 30h slot0: only one answer 30h tag3 is identified select(30h) slot_marker(1) slot1: no answer slot_marker(2) slot2: only one answer 12h 12h tag2 is identified select(12h) slot_marker(3) slot3: collisions slot_marker(4) slot4: no answer 43h 43h 53h 73h slot_marker(5) slot5: collisions slot_marker(6) slot6: no answer 45h 55h slot_marker(n) slotn: no answer slot_marker(f) slotf: no answer 40h 41h 53h 42h 50h 74h all chip_slot_numbers get a new random value pcall16() 40h slot0: collisions slot_marker(1) slot1: only one answer slot_marker(2) slot2: only one answer 42h tag6 is identified select(42h) slot_marker(3) slot3: only one answer select(53h) tag5 is identified 53h slot_marker(4) slot4: only one answer select(74h) tag8 is identified 74h slot_marker(n) slotn: no answer 50h 41h tag4 is identified select(41h) 41h 42h 53h 74h 41h 50h all chip_slot_numbers get a new random value pcall16() slot0: only one answer 50h tag7 is identified select(50h) slot_marker(1) slot1: only one answer but already found for tag4 slot_marker(n) slotn: no answer 50h 41h 43h all chip_slot_numbers get a new random value pcall16() slot0: only one answer slot_marker(3) slot3: only one answer 43h tag1 is identified select(43h) 43h all tags are identified ai07669
srix4k 22/43 anti-clone function the srix4k provides an anti-clone function that allows the application to authentication the device. this function uses reserved data that is stored in the srix4k memory at its time of manufacture. the authentication system is based on a propri- etary challenge/response mechanism which al- lows the application software to authenticate any member of the secure memory tag srxxxx family from stmicroelectronics (of which the srix4k is the prime example). a reader system, based on the st crx14 chip coupler, can check each srix4k tag for authenticity, and protect the appli- cation system against silicon copies or emulators. a complete description of the authentication sys- tem is available under non disclosure agreement (nda) with stmicroelectronics. for more details about this srix4k function, please contact your nearest stmicroelectronics sales office. srix4k commands see the paragraphs below for a detailed descrip- tion of the commands available on the srix4k. the commands and their hexadecimal codes are summarized in table 4. . a brief is given in appen- dix b. . table 4. command code hexadecimal code command 06h-00h initiate() 06h-04h pcall16() x6h slot_marker (sn) 08h read_block(addr) 09h write_block(addr, data) 0ah authenticate(rnd) 0bh get_uid() 0ch reset_to_inventory 0eh select(chip_id) 0fh completion()
23/43 srix4k initiate() command command code = 06h - 00h initiate() is used to initiate the anti-collision se- quence of the srix4k. on receiving the ini- tiate() command, all srix4k devices in ready state switch to inventory state, set a new 8-bit chip_id random value, and return their chip_id value. this command is useful when only one srix4k in ready state is present in the reader field range. it speeds up the chip_id search pro- cess. the chip_slot_number is not used dur- ing initiate() command access. figure 25. initiate request format request parameter: ? no parameter figure 26. initiate response format response parameter: ? chip_id of the srix4k figure 27. initiate frame exchange between reader and srix4k sof initiate crc l crc h eof ai07670 06h 00h 8 bits 8 bits sof chip_id crc l crc h eof ai07671 8 bits 8 bits 8 bits ai07672 reader srix4k sof chip_id crc l crc h eof <-t 0 -> <-t 1 -> sof 06h crc l crc h eof 00h
srix4k 24/43 pcall16() command command code = 06h - 04h the srix4k must be in inventory state to in- terpret the pcall16() command. on receiving the pcall16() command, the srix4k first generates a new random chip_slot_number value (in the 4 least signif- icant bits of the chip_id). chip_slot_number can take on a value between 0 an 15 (1111 b ). the value is retained until a new pcall16() or ini- tiate() command is issued, or until the srix4k is powered off. the new chip_slot_number val- ue is then compared with the value 0000 b . if they match, the srix4k returns its chip_id value. if not, the srix4k does not send any response. the pcall16() command, used together with the slot_marker() command, allows the reader to search for all the chip_ids when there are more than one srix4k device in inventory state present in the reader field range. figure 28. pcall16 request format request parameter: ? no parameter figure 29. pcall16 response format response parameter: ? chip_id of the srix4k figure 30. pcall16 frame exchange between reader and srix4k sof pcall16 crc l crc h eof ai07673 06h 04h 8 bits 8 bits sof chip_id crc l crc h eof ai07671 8 bits 8 bits 8 bits sof 06h crc l crc h eof ai07674 reader srix4k sof chip_id crc l crc h eof <-t 0 -> <-t 1 -> 04h
25/43 srix4k slot_marker(sn) command command code = x6h the srix4k must be in inventory state to in- terpret the slot_marker(sn) command. the slot_marker byte code is divided into two parts: ?b 3 to b 0 : 4-bit command code with fixed value 6. ?b 7 to b 4 : 4 bits known as the slot_number (sn). they assume a value between 1 and 15. the value 0 is reserved by the pcall16() command. on receiving the slot_marker() command, the srix4k compares its chip_slot_number val- ue with the slot_number value given in the command code. if they match, the srix4k returns its chip_id value. if not, the srix4k does not send any response. the slot_marker() command, used together with the pcall16() command, allows the reader to search for all the chip_ids when there are more than one srix4k device in inventory state present in the reader field range. figure 31. slot_marker request format request parameter: ? x: slot number figure 32. slot_marker response format response parameters: ? chip_id of the srix4k figure 33. slot_marker frame exchange between reader and srix4k sof slot_marker crc l crc h eof ai07675 x6h 8 bits 8 bits sof chip_id crc l crc h eof ai07671 8 bits 8 bits 8 bits sof x6h crc l crc h eof ai07676 reader srix4k sof chip_id crc l crc h eof <-t 0 -> <-t 1 ->
srix4k 26/43 select(chip_id) command command code = 0eh the select() command allows the srix4k to enter the selected state. until this command is issued, the srix4k will not accept any other com- mand, except for initiate(), pcall16() and slot_marker(). the select() command re- turns the 8 bits of the chip_id value. an srix4k in selected state, that receives a select() command with a chip_id that does not match its own is automatically switched to deselected state. figure 34. select request format request parameter: ? 8-bit chip_id stored during the anti-collision sequence figure 35. select response format response parameters: ? chip_id of the selected tag. must be equal to the transmitted chip_id figure 36. select frame exchange between reader and srix4k sof select crc l crc h eof ai07677 0eh 8 bits 8 bits 8 bits chip_id sof chip_id crc l crc h eof ai07671 8 bits 8 bits 8 bits ai07678 reader srix4k sof chip_id crc l crc h eof <-t 0 -> <-t 1 -> sof 0eh crc l crc h eof chip_id
27/43 srix4k completion() command command code = 0fh on receiving the completion() command, a srix4k in selected state switches to deacti- vated state and stops decoding any new com- mands. the srix4k is then locked in this state until a complete reset (tag out of the field range). a new srix4k can thus be accessed through a select() command without having to remove the previous one from the field. the completion() command does not generate a response. all srix4k devices not in selected state ignore the completion() command. figure 37. completion request format request parameters: ? no parameter figure 38. completion response format figure 39. completion frame exchange between reader and srix4k sof completion crc l crc h eof ai07679 0fh 8 bits 8 bits ai07680 no response sof 0fh crc l crc h eof ai07681 reader srix4k no response
srix4k 28/43 reset_to_inventory() command command code = 0ch on receiving the reset_to_inventory() command, all srix4k devices in selected state revert to inventory state. the concerned srix4k devices are thus resubmitted to the anti- collision sequence. this command is useful when two srix4k devices with the same 8-bit chip_id happen to be in selected state at the same time. forcing them to go through the anti-collision sequence again allows the reader to generates new pcall16() commands and so, to set new random chip_ids. the reset_to_inventory() command does not generate a response. all srix4k devices that are not in selected state ignore the reset_to_inventory() com- mand. figure 40. reset_to_inventory request format request parameter: ? no parameter figure 41. reset_to_inventory response format figure 42. reset_to_inventory frame exchange between reader and srix4k sof reset_to_inventory crc l crc h eof ai07682 0ch 8 bits 8 bits ai07680 no response sof 0ch crc l crc h eof ai07681 reader srix4k no response
29/43 srix4k read_block(addr) command command code = 08h on receiving the read_block command, the srix4k reads the desired block and returns the 4 data bytes contained in the block. data bytes are transmitted with the least significant byte first and each byte is transmitted with the least significant bit first. the address byte gives access to the 128 blocks of the srix4k (addresses 0 to 127). read_block commands issued with a block ad- dress above 127 will not be interpreted and the srix4k will not return any response, except for the system area located at address 255. the srix4k must have received a select() command and be switched to selected state before any read_block() command can be ac- cepted. all read_block() commands sent to the srix4k before a select() command is is- sued are ignored. figure 43. read_block request format request parameter: ? address: block addresses from 0 to 127, or 255 figure 44. read_block response format response parameters: ? data 1: less significant data byte ? data 2: data byte ? data 3: data byte ? data 4: most significant data byte figure 45. read_block frame exchange between reader and srix4k sof read_block crc l crc h eof ai07684 08h 8 bits 8 bits 8 bits address sof data 1 crc l crc h eof ai07685 8 bits data 2 data 3 data 4 8 bits 8 bits 8 bits 8 bits 8 bits sof data 1 ai07686 data 2 data 3 data 4 reader srix4k crc l crc h eof <-t 0 -> <-t 1 -> sof 08h crc l crc h eof addr
srix4k 30/43 write_block (addr, data) command command code = 09h on receiving the write_block command, the srix4k writes the 4 bytes contained in the com- mand to the addressed block, provided that the block is available and not write-protected. data bytes are transmitted with the least significant byte first, and each byte is transmitted with the least significant bit first. the address byte gives access to the 128 blocks of the srix4k (addresses 0 to 127). write_block commands issued with a block address above 127 will not be interpreted and the srix4k will not return any response, except for the system area located at address 255. the result of the write_block command is submitted to the addressed block. see the follow- ing paragraphs for a complete description of the write_block command: ? resettable otp area (addresses 0 to 4) . ? binary counter (addresses 5 to 6) . ? eeprom (addresses 7 to 127) . the write_block command does not give rise to a response from the srix4k. the reader must check after the programming time, t w , that the data was correctly programmed. the srix4k must have received a select() command and be switched to selected state before any write_block command can be accepted. all write_block commands sent to the srix4k before a select() command is issued, are ig- nored. figure 46. write_block request format request parameters: ? address: block addresses from 0 to 127, or 255 ? data 1: less significant data byte ? data 2: data byte ? data 3: data byte ? data 4: most significant data byte. figure 47. write_block response format figure 48. write_block frame exchange between reader and srix4k sof data 1 crc l crc h eof ai07687 8 bits data 2 data 3 data 4 8 bits 8 bits 8 bits 8 bits 8 bits write_block address 09h 8 bits ai07680 no response data 1 ai07688 data 2 data 3 data 4 reader srix4k crc l crc h eof sof 09h addr no response
31/43 srix4k get_uid() command command code = 0bh on receiving the get_uid command, the srix4k returns its 8 uid bytes. uid bytes are transmitted with the least significant byte first, and each byte is transmitted with the least significant bit first. the srix4k must have received a select() command and be switched to selected state before any get_uid() command can be accept- ed. all get_uid() commands sent to the srix4k before a select() command is issued, are ig- nored. figure 49. get_uid request format request parameter: ? no parameter figure 50. get_uid response format response parameters: ? uid 0: less significant uid byte ? uid 1 to uid 6: uid bytes ? uid 7: most significant uid byte. figure 51. get_uid frame exchange between reader and srix4k power-on state after power-on, the srix4k is in the following state: ? it is in the low-power state. ? it is in ready state. ? it shows highest impedance with respect to the reader antenna field. ? it will not respond to any command except initiate(). sof get_uid crc l crc h eof ai07693 0bh 8 bits 8 bits sof uid 1 crc l crc h eof ai07694 8 bits uid 2 uid 3 uid 4 8 bits 8 bits 8 bits 8 bits 8 bits uid 0 uid 5 8 bits uid 6 8 bits 8 bits uid 7 8 bits s o f crc l crc h e o f ai07692 reader srix4k <-t 0 -> <-t 1 -> s o f crc l crc h e o f 0bh uid 1 uid 2 uid 3 uid 4 uid 0 uid 5 uid 6 uid 7
srix4k 32/43 maximum rating stressing the device above the rating listed in the absolute maximum ratings table may cause per- manent damage to the device. these are stress ratings only and operation of the device at these or any other conditions above those indicated in the operating sections of this specification is not im- plied. exposure to absolute maximum rating con- ditions for extended periods may affect device reliability. refer also to the stmicroelectronics sure program and other relevant quality docu- ments. table 5. absolute maximum ratings note: 1. mil. std. 883 - method 3015 2. esd test: iso10373-6 for proximity cards symbol parameter min. max. unit t stg , h stg , t stg storage conditions wafer 15 25 c 23 months kept in its antistatic bag a3, a4, a5 15 25 c 40% 60% rh 2years i cc supply current on ac0 / ac1 ?20 20 ma v max input voltage on ac0 / ac1 ?7 7 v v esd electrostatic discharge voltage machine model 1 ?100 100 v human body model 1 ?1000 1000 v human body model 2 ?4000 4000 v
33/43 srix4k dc and ac parameters table 6. operating conditions table 7. dc characteristics table 8. ac characteristics note: 1. all timing measurements were performed on a reference antenna with the following characteristics: external size: 75mm x 48mm number of turns: 3 width of conductor: 1mm space between 2 conductors: 0.4mm value of the coil: 1.4h tuning frequency: 14.4mhz. symbol parameter min. max. unit t a ambient operating temperature ?20 85 c symbol parameter condition min max unit v cc regulated voltage 2.5 3.5 v i cc supply current (active in read) v cc =3.0v 100 a i cc supply current (active in write) v cc =3.0v 250 a v ret retromodulation induced voltage iso10373-6 20 mv c tun internal tuning capacitor 70pf at 13.56mhz 64 78 pf symbol parameter condition min max unit f cc external rf signal frequency 13.553 13.567 mhz mi carrier carrier modulation index mi=(a-b)/(a+b) 8 14 % t rfr ,t rff 10% rise and fall times 0.8 2.5 s t rfsbl minimum pulse width for start bit etu = 128/f cc 9.44 s t jit ask modulation data jitter coupler to srix4k ?2 +2 s t min cd minimum time from carrier generation to first data 5ms f s subcarrier frequency f cc /16 847.5 khz t 0 antenna reversal delay 128/f s 151 s t 1 synchronization delay 128/f s 151 s t 2 answer to new request delay 14 etu 132 s t dr time between request characters coupler to srix4k 0 57 s t da time between answer characters srix4k to coupler 0 s t w programming time for write with no auto-erase cycle (otp) 3ms with auto-erase cycle (eeprom) 5ms binary counter decrement 7 ms
srix4k 34/43 figure 52. srix4k synchronous timing, transmit and receive ab t rff t rfr t rfsbl t min cd ? cc ask modulated signal from the reader to the contactless device data 0 eof 847khz t dr t 0 t 1 frame transmission between the reader and the contactless device frame transmitted by the reader in ask frame transmitted by the srix4k 1 1 t dr in bpsk data 0 1 data 0 t da t da sof 1 0 1 1 start 0 t rfsbl t rfsbl t rfsbl t jit t jit t jit t jit t jit t rfsbl t rfsbl data jitter on frame transmitt ed by the reader in ask ai09052
35/43 srix4k package mechanical figure 53. a3 antenna specification table 9. a3 antenna specification symbol parameter type min max unit a coil width 38 37.5 38.5 mm b coil length 38 37.5 38.5 mm a1 inlay width 43 42.5 43.5 mm b1 inlay length 43 42.5 43.5 mm overall thickness of copper antenna coil 110 90 130 m silicon thickness 180 165 195 m q unloaded q value 40 f nom unloaded free-air resonance 15.1 mhz p a h-field energy for device operation 0.5 114 a/m dba/m a b1 a1 ai09046b b
srix4k 36/43 figure 54. a4 antenna specification table 10. a4 antenna specification symbol parameter type min max unit a coil width 15 14.5 15.5 mm b coil length 15 14.5 15.5 mm a1 inlay width 19 18.5 19.5 mm b1 inlay length 19 18.5 19.5 mm overall thickness of copper antenna coil 110 90 130 m silicon thickness 180 165 195 m q unloaded q value 30 f nom unloaded free-air resonance 14.5 mhz p a h-field energy for device operation 1.5 123.5 a/m dba/m ai07696b b a a1 b1
37/43 srix4k figure 55. a5 antenna specification table 11. a5 antenna specification symbol parameter type min max unit a coil width 42 41.5 42.5 mm b coil length 65 64.5 65.5 mm a1 inlay width 46 45.5 46.5 mm b1 inlay length 70 69.5 70.5 mm overall thickness of copper antenna coil 140 130 150 m silicon thickness 180 165 195 m q unloaded q value 30 f nom unloaded free-air resonance 14.8 mhz p a h-field energy for device operation 0.25 108 a/m dba/m a b a1 ai09071b b1
srix4k 38/43 part numbering table 12. ordering information scheme note: devices are shipped from the factory with the memory content bits erased to 1. for a list of available options (speed, package, etc.) or for further information on any aspect of this device, please contact your nearest st sales office. example: srix4k ? w4 / xxx device type srix4k package w4 =180 m 15 m unsawn wafer sbn18= 180m 15 m bumped and sawn wafer on 8-inch frame a3t= 38mm x 38mm copper antenna on continuous tape a3s= 38mm x 38mm copper singulated adhesive antenna on tape a4t= 15mm x 15mm copper antenna on continuous tape a4s= 15mm x 15mm copper singulated adhesive antenna on tape a5t= 42mm x 65mm copper antenna on continuous tape a5s= 42mm x 65mm copper singulated adhesive antenna on tape customer code xxx = given by stmicroelectronics
39/43 srix4k appendix a. iso14443 type b crc calculation #include #include #include #include #define byte unsigned char #define ushort unsigned short unsigned short updatecrc(byte ch, ushort *lpwcrc) { ch = (ch^(byte)((*lpwcrc) & 0x00ff)); ch = (ch^(ch<<4)); *lpwcrc = (*lpwcrc >> 8)^((ushort)ch << 8)^((ushort)ch<<3)^((ushort)ch>>4); return(*lpwcrc); } void computecrc(char *data, int length, byte *transmitfirst, byte *transmitsecond) { byte chblock; ushortt wcrc; wcrc = 0xffff; // iso 3309 do { chblock = *data++; updatecrc(chblock, &wcrc); } while (--length); wcrc = ~wcrc; // iso 3309 *transmitfirst = (byte) (wcrc & 0xff); *transmitsecond = (byte) ((wcrc >> 8) & 0xff); return; } int main(void) { byte buffcrc_b[10] = {0x0a, 0x12, 0x34, 0x56}, first, second, i; printf("crc-16 g(x) = x^16 + x^12 + x^5 + 1?); printf("crc_b of [ "); for(i=0; i<4; i++) printf("%02x ",buffcrc_b[i]); computecrc(buffcrc_b, 4, &first, &second); printf("] transmitted: %02x then %02x.?, first, second); return(0);
srix4k 40/43 appendix b. srix4k command summary figure 56. initiate frame exchange between reader and srix4k figure 57. pcall16 frame exchange between reader and srix4k figure 58. slot_marker frame exchange between reader and srix4k figure 59. select frame exchange between reader and srix4k figure 60. completion frame exchange between reader and srix4k ai07672 reader srix4k sof chip_id crc l crc h eof <-t 0 -> <-t 1 -> sof 06h crc l crc h eof 00h sof 06h crc l crc h eof ai07674 reader srix4k sof chip_id crc l crc h eof <-t 0 -> <-t 1 -> 04h sof x6h crc l crc h eof ai07676 reader srix4k sof chip_id crc l crc h eof <-t 0 -> <-t 1 -> ai07678 reader srix4k sof chip_id crc l crc h eof <-t 0 -> <-t 1 -> sof 0eh crc l crc h eof chip_id sof 0fh crc l crc h eof ai07681 reader srix4k no response
41/43 srix4k figure 61. reset_to_inventory frame exchange between reader and srix4k figure 62. read_block frame exchange between reader and srix4k figure 63. write_block frame exchange between reader and srix4k figure 64. get_uid frame exchange between reader and srix4k sof 0ch crc l crc h eof ai07681 reader srix4k no response sof data 1 ai07686 data 2 data 3 data 4 reader srix4k crc l crc h eof <-t 0 -> <-t 1 -> sof 08h crc l crc h eof addr data 1 ai07688 data 2 data 3 data 4 reader srix4k crc l crc h eof sof 09h addr no response s o f crc l crc h e o f ai07692 reader srix4k <-t 0 -> <-t 1 -> s o f crc l crc h e o f 0bh uid 1 uid 2 uid 3 uid 4 uid 0 uid 5 uid 6 uid 7
srix4k 42/43 revision history table 13. document revision history date versio n description of revision 28-nov-2002 1.0 document written 17-jul-2003 1.1 data briefing extracted 12-mar-2004 2.0 first public release of full datasheet 26-apr-2004 3.0 correction to memory map 29-nov-2004 4.0 package mechanical section revised. 13-dec-2004 5.0 v ret and c tun parameters added to table 7., dc characteristics .
43/43 srix4k information furnished is believed to be accurate and reliable. however, stmicroelectronics assumes no responsibility for the co nsequences of use of such information nor for any infringement of patents or other rights of third parties which may result from its use. no license is granted by implication or otherwise under any patent or patent rights of stmicroelectronics. specifications mentioned in this publicati on are subject to change without notice. this publication supersedes and replac es all information previously supplied. stmicroelectronics prod ucts are not authorized for use as critical components in life support devices or systems without express written approval of stmicroelectro nics. the st logo is a registered trademark of stmicroelectronics. all other names are the property of their respective owners ? 2004 stmicroelectronics - all rights reserved stmicroelectronics group of companies australia - belgium - brazil - canada - china - czech republic - finland - france - germany - hong kong - india - israel - ital y - japan - malaysia - malta - morocco - singapore - spain - sweden - switzerland - united kingdom - united states of america www.st.com

▲Up To Search▲

Price & Availability of SRIX4K-W41GE

	To Download SRIX4K-W41GE Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .